Skip to content

docs: update RFC links to use the official RFC editor URLs - #245

Merged
mosuem merged 2 commits into
google:masterfrom
berkaycatak:updated-rfc-links
Jul 17, 2026
Merged

docs: update RFC links to use the official RFC editor URLs#245
mosuem merged 2 commits into
google:masterfrom
berkaycatak:updated-rfc-links

Conversation

@berkaycatak

Copy link
Copy Markdown
Contributor

This is my first contribution to the organization, and I'm honestly excited. 🙃

I noticed a TODO comment in webcrypto.pbkdf2.dart requesting to rewrite RFC links, so I decided to tackle it.

Updated all RFC documentation links from the legacy tools.ietf.org domain to the official rfc-editor.org domain as requested in the TODO comment. The old URLs redirect to datatracker.ietf.org, but rfc-editor.org is the canonical source specified in the codebase TODO.

Changes

  • Updated RFC links in 11 files across the codebase
  • No functional changes, documentation only

Test plan

  • Verified all new links are accessible and point to the correct RFC sections
  • No code logic was modified, only documentation URLs

@mosuem

mosuem commented Jul 17, 2026

Copy link
Copy Markdown
Collaborator

Solved in #241 , but still merging to remove the TODO :) Sorry for the long wait!

@mosuem
mosuem merged commit 9aefffc into google:master Jul 17, 2026
14 checks passed
HamdaanAliQuatil added a commit that referenced this pull request Jul 24, 2026
* Move Flutter demo app into example/webcrypto_demo_flutter_app/ (#284)

* refactor: move Flutter demo app into example/webcrypto_demo_flutter_app/ (#283)

* chore: fix references to the relocated example app (#283)

* chore: ignore unknown dartdoc example directive (#294)

* refactor: replace runtime symbol lookup with direct FFI  bindings (#279)

* refactor: replace runtime symbol lookup with direct FFI  bindings

* refactor: replace runtime symbol lookup with direct FFI
  bindings

* refactor: generate direct FFI bindings with ffigen

* refactor: remove stale symbol table files

* refactor: use Native.addressOf for EVP_PKEY finalizer

* Reject imported EC and RSA keys with trailing bytes (#251)

* Reject imported EC and RSA keys with trailing bytes

* Add regression tests for issue 60 (trailing bytes in key imports)

* Finalize regression tests for issue 60: hardcoded keys and browser compatibility

* Update lib/src/testing/regression/issue_60_trailing_bytes.dart

Co-authored-by: Jonas Finnemann Jensen <jopsen@gmail.com>

* Update lib/src/testing/regression/issue_60_trailing_bytes.dart

Co-authored-by: Jonas Finnemann Jensen <jopsen@gmail.com>

* Fix trailing bytes regression fixture

* Minimize trailing bytes fixture diff

* Fix trailing bytes regression on web wasm

* fix: FFI key import memory leaks and make trailing bytes tests

---------

Co-authored-by: Jonas Finnemann Jensen <jopsen@gmail.com>

* ci: add FFI memory-safety test lane (#295)

* ci: add FFI memory-safety test lane

* test: separate Valgrind runner from FFI workload

* ci: run Valgrind in existing Linux job

* refactor(js): fix JSDomException checks for wasm compatibility (#306)

* refactor(js): fix JSDomException checks for wasm compatibility

Resolve invalid_runtime_check_with_js_interop_types warnings for JSDomException.

Instead of directly catching the extension type JSDomException or checking e is JSObject, we catch generic objects, cast them to JSAny?, and check if they are JSDomException instances using isA<subtle.JSDomException>().

This avoids platform-inconsistent runtime checks that behave incorrectly under dart2wasm where extension types are runtime-erased.

* fix libraries

* refactor(js): fix JSDomException type-checking crash under WASM

Resolve _TypeError when casting generic exceptions to JSAny? under dart2wasm.

* fix(testing): wire AES-GCM tagLength vectors (#312)

* Fix AES-CTR large chunk handling (#309)

* fix(aes-ctr): handle partial chunks larger than buffer

* test(aes-ctr): refine large chunk coverage

* fix(derive-bits): support zero-length results (#321)

* docs: update RFC links to use the official RFC editor URLs (#245)

Co-authored-by: Moritz <27859082+mosuem@users.noreply.github.com>

* docs: move HMAC importRawKey example to file (#293)

* chore: mark unsupported code paths with coverage:ignore (#327)

* chore: mark unsupported code paths with coverage:ignore

* test: mark impl_stub as coverage:ignore-file

* test: ignore unreachable curve fallbacks in EC helpers

* docs: correct JWK use value for AES keys (#330)

* correct JWK use value for AES keys

* correct JWK use value for AES keys

* correct JWK use value for AES keys

* Document maximum deriveBits length for ECDH curves (#289)

Updates documentation on EcdhPrivateKey.deriveBits to include
the maximum number of bits that can be derived for each curve:

  * EllipticCurve.p256 — up to 256 bits
  * EllipticCurve.p384 — up to 384 bits
  * EllipticCurve.p521 — up to 528 bits

Also adds test coverage for all three curves at their maximum
derive lengths in the ECDH test runner.

Fixes #130

* Upgrade native_toolchain_cmake to v0.3 (#336)

This new version improves Android SDK detection:
rainyl/native_toolchain_cmake#31

* fix: use canonical RSA-OAEP JWK alg for SHA-1 (#337)

---------

Co-authored-by: Samar Borkar <128998523+Samarborkar@users.noreply.github.com>
Co-authored-by: Musharaf Khan Pathan <135562339+Apple-beep@users.noreply.github.com>
Co-authored-by: HamdaanAliQuatil <96776914+HamdaanAliQuatil@users.noreply.github.com>
Co-authored-by: Harshita Yadav <seemayadavanuj123@gmail.com>
Co-authored-by: Jonas Finnemann Jensen <jopsen@gmail.com>
Co-authored-by: Kevin Moore <kevmoo@users.noreply.github.com>
Co-authored-by: Berkay Çatak <34205493+berkaycatak@users.noreply.github.com>
Co-authored-by: Moritz <27859082+mosuem@users.noreply.github.com>
Co-authored-by: AquibAquil <96966923+AquibAquil@users.noreply.github.com>
Co-authored-by: w1boost1889M <63419938+w1boost1889M@users.noreply.github.com>
Co-authored-by: Syed Moiz Ali <100577359+Syed-Moiz-Ali@users.noreply.github.com>
Co-authored-by: Simon Ser <contact@emersion.fr>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants